fix: ci#3204
Conversation
Added a step to debug disk usage after the build process, providing insights into disk space and large files.
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. WalkthroughReplaces the broad, system-wide "Extreme Disk Cleanup" in the CentOS CI job with workspace-scoped deletions under Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR optimizes the CI workflow disk cleanup strategy for the CentOS build job. The changes replace an aggressive, system-wide cleanup approach with targeted cleanup of specific project-related directories and build artifacts.
Key changes:
- Simplified the "Extreme Disk Cleanup" step with more focused cleanup commands
- Removed aggressive system-wide cleanup operations (e.g.,
/usr/local/share/*,/usr/share/doc/*) - Targeted cleanup of specific build artifacts and large static libraries
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| rm -rf /__w/pikiwidb/pikiwidb/buildtrees 2>/dev/null || true | ||
| rm -rf /__w/pikiwidb/pikiwidb/deps 2>/dev/null || true | ||
| find /__w/pikiwidb/pikiwidb -type f \( -name "librocksdb.a" -o -name "libprotoc.a" -o -name "libprotobuf.a" \) -delete 2>/dev/null || true | ||
| find /__w/pikiwidb/pikiwidb -type f \( -name "*.o" -o -name "*.a" -o -name "*.la" -o -name "*.so" -o -name "*_test" \) ! -path "*/build/pika" -delete 2>/dev/null || true | ||
| rm -rf /__w/pikiwidb/pikiwidb/.git 2>/dev/null || true |
There was a problem hiding this comment.
The hardcoded path /__w/pikiwidb/pikiwidb should be replaced with ${{ github.workspace }} for portability and to avoid issues if the repository or GitHub Actions runner configuration changes. This pattern is used consistently throughout the workflow file (see lines 65, 68, 74, 87, 96, etc.).
| echo "Largest directories:" | ||
| du -h --max-depth=2 / 2>/dev/null | sort -hr | head -20 | ||
| rm -rf /__w/pikiwidb/pikiwidb/buildtrees 2>/dev/null || true | ||
| rm -rf /__w/pikiwidb/pikiwidb/deps 2>/dev/null || true |
There was a problem hiding this comment.
Trailing whitespace detected after || true. Consider removing it for consistency with YAML formatting standards.
| rm -rf /__w/pikiwidb/pikiwidb/deps 2>/dev/null || true | |
| rm -rf /__w/pikiwidb/pikiwidb/deps 2>/dev/null || true |
| find /__w/pikiwidb/pikiwidb -type f \( -name "librocksdb.a" -o -name "libprotoc.a" -o -name "libprotobuf.a" \) -delete 2>/dev/null || true | ||
| find /__w/pikiwidb/pikiwidb -type f \( -name "*.o" -o -name "*.a" -o -name "*.la" -o -name "*.so" -o -name "*_test" \) ! -path "*/build/pika" -delete 2>/dev/null || true | ||
| rm -rf /__w/pikiwidb/pikiwidb/.git 2>/dev/null || true | ||
| df -h |
There was a problem hiding this comment.
Trailing whitespace detected after df -h. Consider removing it for consistency with YAML formatting standards.
| df -h | |
| df -h |
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.